-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FIX] Replaced the latest version tag with a baked-in version #390
Conversation
Reviewer's Guide by SourceryThis PR implements a more reliable versioning system by reading the version from package.json instead of fetching it from GitHub's API. The Docker workflows have been updated to manage this version: the release workflow now updates package.json with the release version and commits the change, while the nightly build workflow updates it with the latest commit SHA without committing. No diagrams generated as the changes look simple and do not need a visual representation. File-Level Changes
Assessment against linked issues
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
✅ Deploy Preview for neurobagel-query ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @rmanaem - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟡 General issues: 2 issues found
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @rmanaem for this! Looks very nice and solves an important problem 🎉
I left some comments, mainly clarity. But please also open an issue to explore ways to make the package.json version bump part of the release in the future. I think that'd be clearer
🧑🍳
After an in-length discussion, we decided to move to implementing a workflow to run on PR when labels have been changed (action type: labeled, see docs). This workflow will calculate the new version using auto version (see docs), update the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @rmanaem, this looks very good!
Left one question, otherwise 🧑🍳
Changes proposed in this pull request:
package.json
package.json
to match that of GitHubpackage.json
package.json
to the latest SHAChecklist
This section is for the PR reviewer
[ENH]
,[FIX]
,[REF]
,[TST]
,[CI]
,[MNT]
,[INF]
,[MODEL]
,[DOC]
) (see our Contributing Guidelines for more info)skip-release
(to be applied by maintainers only)Closes #XXXX
query-tool-results
files in the neurobagel_examples repo have been regeneratedFor new features:
For bug fixes:
Summary by Sourcery
Replace the dynamic fetching of the latest release tag with a static version from package.json and update Docker workflows to manage versioning during builds.
Bug Fixes:
CI: